Triple
T32554307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larfleeze |
E832056
|
entity |
| Predicate | ringCorps |
P92676
|
FINISHED |
| Object | Orange Lantern Corps |
—
|
NE NERFINISHED |
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: Orange Lantern Corps | Statement: [Larfleeze, ringCorps, Orange Lantern Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringCorps Context triple: [Larfleeze, ringCorps, Orange Lantern Corps]
-
A.
ringType
Indicates the specific kind or category of ring associated with an entity or relationship.
-
B.
ringOrigin
Indicates the source or starting point from which a ring (such as a circular structure, feature, or formation) arises or is generated.
-
C.
ringPower
Indicates that an entity possesses or exerts the special power or influence associated with a particular ring.
-
D.
ringContained
Indicates that one ring-shaped object is entirely enclosed within the spatial bounds of another ring-shaped object.
-
E.
associatedWithRing
chosen
Indicates that an entity has a connection or relationship with a specific ring, such as ownership, membership, or involvement.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c95cc481909ab34c9e889a6281 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.