Triple
T37458580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Threes! |
E930860
|
entity |
| Predicate | hasCopycat |
P144124
|
FINISHED |
| Object | 2048 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2048 | Statement: [Threes!, hasCopycat, 2048]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCopycat Context triple: [Threes!, hasCopycat, 2048]
-
A.
hasCopy
Indicates that one entity possesses, contains, or maintains a duplicate or instance of another entity.
-
B.
isCopiedBy
Indicates that an entity serves as the source from which another entity is duplicated or reproduced.
-
C.
hasDoppelganger
chosen
Indicates that an entity has a counterpart or double that closely resembles it, often in appearance, behavior, or role.
-
D.
hasCopyleft
Indicates that a work, license, or component is subject to copyleft terms requiring derivative or combined works to be distributed under the same or compatible license conditions.
-
E.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.