Triple
T23560704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muppet Labs |
E579227
|
entity |
| Predicate | hasNotableProp |
P642
|
FINISHED |
| Object | lab coats |
—
|
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: lab coats | Statement: [Muppet Labs, hasNotableProp, lab coats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProp Context triple: [Muppet Labs, hasNotableProp, lab coats]
-
A.
hasNotablePropertyNamedAfter
Indicates that an entity possesses a notable property or attribute that is named in honor of, or derived from, another entity.
-
B.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
C.
hasNotableItem
Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
-
D.
isNotable
Indicates that an entity is recognized as significant, prominent, or worthy of attention within a particular context or domain.
-
E.
hasNotableFeature
chosen
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af680ee88190a23a6f9fed7ae757 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:15 p.m.