Triple
T37476850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-23 |
E931303
|
entity |
| Predicate | isEndOfLineCodeFor |
P80183
|
FINISHED |
| Object | Młociny |
—
|
NE NERFINISHED |
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: Młociny | Statement: [A-23, isEndOfLineCodeFor, Młociny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndOfLineCodeFor Context triple: [A-23, isEndOfLineCodeFor, Młociny]
-
A.
isLastOfLineBefore
Indicates that one entity is the final element in a sequence immediately preceding a specified boundary, transition, or next segment.
-
B.
hasLineCharacter
Indicates that one entity possesses or includes a specific character or symbol that appears within a line of text or sequence.
-
C.
definesLineTerminator
chosen
Indicates that one entity specifies what character or sequence of characters marks the end of a line for another entity.
-
D.
lineTerminusFor
Indicates that one entity serves as an endpoint or terminus of a particular line or linear feature represented by another entity.
-
E.
endOfLineDescendantOf
Indicates that one entity is a descendant of another in a hierarchy and appears at the terminal (end-of-line) position of that descendant chain.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.