Triple
T29389246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PrintDocumentAdapter |
E745331
|
entity |
| Predicate | onStart |
P166712
|
FINISHED |
| Object | calledBeforeFirstLayout |
—
|
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: calledBeforeFirstLayout | Statement: [PrintDocumentAdapter, onStart, calledBeforeFirstLayout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onStart Context triple: [PrintDocumentAdapter, onStart, calledBeforeFirstLayout]
-
A.
exportStart
Indicates the point in time or event at which an export process or outbound transfer of goods, data, or resources begins.
-
B.
mainStartingPoint
Indicates the primary location or position from which an event, process, or path begins.
-
C.
startOfApplicationCycle
Indicates the point in time when a new application cycle begins for a given process or program.
-
D.
startedShowOn
Indicates that an entity initiated or began broadcasting or presenting a particular show on a specified platform, channel, or service.
-
E.
startDuring
Indicates that one event or interval begins at some point strictly within the duration of another event or interval, but not at its start.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d578608190962d35116a01420c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:41 p.m.