Triple
T23313261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LFS |
E590636
|
entity |
| Predicate | layoutUnit |
P151827
|
FINISHED |
| Object | segment |
—
|
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: segment | Statement: [LFS, layoutUnit, segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutUnit Context triple: [LFS, layoutUnit, segment]
-
A.
nativeUnit
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
B.
registrationUnit
Indicates that one entity serves as the official unit or body responsible for registering, recording, or enrolling another entity.
-
C.
representationUnit
Indicates a relationship where one entity serves as the representational unit or basic representational component used to express, encode, or stand in for another entity or concept.
-
D.
coordinateUnit
Indicates that one unit serves as a coordinate or reference unit relative to another in a measurement, spatial, or organizational context.
-
E.
definedInUnit
Indicates that something (such as a symbol, element, or construct) is declared or established within a particular unit, module, or file.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:06 p.m.