Triple
T18024055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conchifera |
E431200
|
entity |
| Predicate | shellLocation |
P129496
|
FINISHED |
| Object | external shell |
—
|
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: external shell | Statement: [Conchifera, shellLocation, external shell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellLocation Context triple: [Conchifera, shellLocation, external shell]
-
A.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
B.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
C.
locationOfCommand
Indicates that a specified place or facility serves as the site from which a particular command or authority is exercised.
-
D.
binaryLocation
Indicates that one entity is the physical or logical location where another binary or executable artifact resides.
-
E.
coreLocation
Indicates that one entity serves as the central or primary location associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c475dc819086c4cd86d663791f |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.