Triple
T16633660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squidward's Easter Island head house |
E404141
|
entity |
| Predicate | hasDoorLocation |
P12030
|
FINISHED |
| Object | front center of the Moai face |
—
|
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: front center of the Moai face | Statement: [Squidward's Easter Island head house, hasDoorLocation, front center of the Moai face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoorLocation Context triple: [Squidward's Easter Island head house, hasDoorLocation, front center of the Moai face]
-
A.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
B.
doorLocation
chosen
Indicates the spatial position or placement of a door relative to a reference structure or area.
-
C.
hasDoorSide
Indicates that one entity represents a specific side or face of a door in relation to another entity.
-
D.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
E.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e7d4a48190a9b4a14ecbb2a14b |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.