Triple
T32358522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etropus |
E826796
|
entity |
| Predicate | lateralCompression |
P200547
|
FINISHED |
| Object | strongly compressed body |
—
|
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: strongly compressed body | Statement: [Etropus, lateralCompression, strongly compressed body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lateralCompression Context triple: [Etropus, lateralCompression, strongly compressed body]
-
A.
hasLateralStructure
Indicates that one entity possesses or exhibits a structural feature oriented to or located on its side(s).
-
B.
numberOfLaterals
Indicates the count of lateral branches or side elements associated with a given entity or structure.
-
C.
boundedLaterallyBy
Indicates that one entity has its sides or lateral boundaries defined or constrained by another entity.
-
D.
laterSide
Indicates that one entity is positioned on the side that comes later or is farther along a defined directional or temporal axis relative to another entity.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side of 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
| PDg | Predicate description generation | batch_69ff956cd640819081efc31f313690b0 |
completed | May 9, 2026, 8:13 p.m. |
Created at: May 1, 2026, 12:49 a.m.