Triple
T5015361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinite Loop campus |
E112728
|
entity |
| Predicate | hasLogoDisplay |
P36877
|
FINISHED |
| Object | large Apple logo at main entrance |
—
|
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: large Apple logo at main entrance | Statement: [Infinite Loop campus, hasLogoDisplay, large Apple logo at main entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogoDisplay Context triple: [Infinite Loop campus, hasLogoDisplay, large Apple logo at main entrance]
-
A.
hasLogoText
Indicates that an entity’s logo includes specific textual content or wording.
-
B.
logoUsedIn
chosen
Indicates that a particular logo is employed or displayed within a specified context, medium, or artifact.
-
C.
hasFormerLogo
Indicates that an entity is associated with a logo it used in the past but no longer uses.
-
D.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
E.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732e0b848190858407920e7aefd0 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.